---
id: 660686845b5e788def3527ca
title: Task 9
challengeType: 22
dashedName: task-9
---

<!--
AUDIO REFERENCE:
Entire dialogue
-->

# --description--

This task involves summarizing the conversation between Sophie and Brian about how to analyze a new API's documentation.

# --fillInTheBlank--

## --sentence--

`Sophie is working with a new API and is unsure how to _ its documentation effectively. Brian suggests she should _ by checking the _ and _ in the documentation for a clear idea of what the API offers. He then advises that once she's _ the endpoints, she should _ the _ and _ for each. This helps in understanding the API's use in projects. Sophie thanks Brian and says she'll give it a _.`

## --blanks--

`analyze`

### --feedback--

It means to examine in detail. Sophie wants to understand how to look at the API documentation closely.

---

`begin`

### --feedback--

It means to start. Brian advises starting with the endpoints and routes.

---

`endpoints`

### --feedback--

They are specific locations where API requests are made. Brian mentions these as starting points.

---

`routes`

### --feedback--

They are paths defined in the API for handling requests. They are key parts of the documentation.

---

`identified`

### --feedback--

It means recognized or discovered. Sophie needs to recognize the endpoints first.

---

`read`

### --feedback--

It means to look at and comprehend text. Brian suggests reading the details for each endpoint.

---

`descriptions`

### --feedback--

They give details about something. Sophie should read the details about each endpoint.

---

`examples`

### --feedback--

They are specific instances showing how something works. They are important for understanding the API.

---

`shot`

### --feedback--

It means to try or attempt. Sophie decides to try out Brian's suggestions.
